Systems and methods for using graphical representations to manage query results

ABSTRACT

Described are systems and methods for changing query result data graphically displayed on an electronic device. A query of a data repository is performed. A graphical representation of a set of query results identified from the query is displayed. The query results include a plurality of query result records. The graphical representation includes a first node corresponding to a first record field value and a second node corresponding to a second record field value. A region proximal to the first node displays a query result record having the first record field value. A query result record having the first record field value is selected. A field value of a selected query result record is changed from the first record field value to the second record field value by transitioning the selected query result record to a region proximal to the second node.

RELATED APPLICATIONS

This application is a continuation application claiming the benefit ofthe filing date of U.S. patent application Ser. No. 13/159,682, filedJun. 14, 2011, entitled “Systems and Methods for Using GraphicalRepresentations to Manage Query Results,” contents of which areincorporated by reference herein in their entirety.

FIELD OF THE INVENTION

The present invention relates generally to the use of database queryresults, and more specifically, to systems and methods for changingcontents of a query result set displayed according to a graphicalrepresentation.

BACKGROUND

Data retrieval tools are widely available for querying a database anddisplaying the query results in a grid or table to a computer user. Thegrid or table is generally organized into rows and columns. Query resultvalues can be displayed at data fields arranged as cells formed by therows and columns. A user can define selection criteria and/or customizethe query results by column sorting, filtering based on field values,and the like, in order for the query results to be displayed at a usefulmanner to the user.

Data visualization techniques can be applied when a user selects one ormore rows of a database table, whereby the selected items can bedisplayed as a histogram, bar graph, and the like. Once the graph isdisplayed according to a conventional approach, the underlying contentscannot be changed.

BRIEF SUMMARY

An embodiment features a method for changing query result datagraphically displayed on an electronic device. In accordance with themethod, a query of a data repository is performed. A graphicalrepresentation of a set of query results identified from the query isdisplayed. The set of query results includes a plurality of query resultrecords. The graphical representation includes a first locationcorresponding to a first record field value and a second locationcorresponding to a second record field value. At least one query resultrecord having the first record field value is displayed at the firstlocation. A query result record of the at least one query result recordhaving the first record field value is selected. A field value of aselected query result record is changed from the first record fieldvalue to the second record field value by transitioning the selectedquery result record to a region proximal to the second location of thegraphical representation.

Another embodiment features a method for changing query result datagraphically displayed on an electronic device. In accordance with themethod, a query of a data repository is performed. A graphicalrepresentation of a set of query results identified from the query isdisplayed. The set of query results includes a plurality of query resultrecords. The graphical representation includes a first nodecorresponding to a first record field value. A region proximal to thefirst node displays at least one query result record having the firstrecord field value. A region proximal to the second node displays amodifiable field. A second record field value is entered into themodifiable field. The second node corresponds to the second record fieldvalue. A query result record of the at least one query result recordhaving the first record field value is selected. A field value of aselected query result record is changed from the first record fieldvalue to the second record field value by transitioning the selectedquery result record to a region proximal to the second node displayingthe modifiable field.

Another embodiment features a method for modifying data retrieved from adatabase query. In accordance with the method, a result set isdetermined from a database query. The result set includes a plurality ofdatabase records comprising a first database record and a seconddatabase record. A graphical representation of a data relationshipbetween the first database record and the second database record isdisplayed. The graphical representation includes a plurality of verticesand at least one arc extending between the vertices. The first databaserecord and the second database record is displayed at a region proximalto at least one of the vertices. A graphical representation of aplurality of record field values is displayed. Each record field valuecorresponds to a vertex. At least one of the first and second databaserecords is selected. A displayed record field value is selected. Theselected at least one of the first and second database records ischanged to include the selected displayed record field value.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The above and further advantages of this invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings, in which like numerals indicate likestructural elements and features in various figures. The drawings arenot necessarily to scale, emphasis instead being placed uponillustrating the principles of the invention.

FIG. 1 is a block diagram of a graphical display system in whichembodiments of the present inventive concepts can be implemented;

FIG. 2 is a block diagram of a query result management system, inaccordance with an embodiment;

FIG. 3 is a flow diagram of a method for using a graphicalrepresentation of a query result set to modify query data, in accordancewith an embodiment;

FIG. 4 is a flow diagram of a method for using a graphicalrepresentation of a query result set to modify query data, in accordancewith another embodiment;

FIG. 5 is a screenshot of a query result set displayed at a databasefile, in accordance with an embodiment;

FIG. 6 is an illustration of the query results of FIG. 5 arranged in afield graph, in accordance with embodiment;

FIG. 7 is an illustration of a record field value change in the fieldgraph of FIG. 6, in accordance with an embodiment;

FIG. 8 is an illustration of the query results of FIG. 5 arranged inanother field graph, in accordance with an embodiment;

FIG. 9 is an illustration of the query results of FIG. 5 arranged inanother field graph, in accordance with an embodiment; and

FIG. 10 is an illustration of the query results of FIG. 5 arranged inanother field graph, in accordance with an embodiment.

DETAILED DESCRIPTION

In the following description, specific details are set forth although itshould be appreciated by one of ordinary skill that the systems andmethods can be practiced without at least some of the details. In someinstances, known features or processes are not described in detail so asnot to obscure the present invention.

The embodiments described herein provide for a presentation of data thatallows users to make straightforward and natural changes to query resultrecords without relying on conventional hard-to-discover context menuoptions, query modifications, or separate dialogs. The embodimentsovercome limitations regarding conventional approaches for temporarilyviewing different visual representations of a query result set for thepurpose of making edits to its contents. One such approach is for a userto view a form in a display window that represents a single detailedrecord corresponding to a result row of a database table. Anotherapproach is for a user to modify query criteria to change the display ofthe query results, or perform column sorting or related adjustments, forexample, to rearrange a tabular representation of the data.

The embodiments referred to herein also overcome limitations regardingconventional approaches when users desire to make multiple changes tothe query results quickly or to perform an action on multiple records atonce. One approach is for a user to select multiple rows of a queryresults table, and modify the selection by using a context menu toinvoke a batch update. For example, a drag-and-drop operation can beperformed where the selected records are moved to a dialog boxconfigured with a field value, whereby the selected records can each bechanged to that field value. However, batch updates are generally madewithout a clear understanding of the relationship of the selected itemswith respect to the other elements of the result set. The batch updateoperation is also oriented to a subset of data in the result set, forexample, a single field value common to a handful of records. Batchupdate dialog boxes and/or context menu options often display fieldvalues for certain records but do not display other records in theresult set that share those values.

Another conventional approach is that users can select multiple recordsof a result set at the same time, and rearrange the result setaccordingly by column sorting or modifying an existing query to allowfor an easier selection of the rows that they want to change. Whenchanges are made to the result set in this manner, problems can arise ifthe modified rows are re-inserted in sorted order they will disappearfrom view and that by leaving the modified rows in place is anindication of the result set no longer properly being sorted.

In brief overview, the present inventive concepts include systems andmethods for visually presenting a query result set in accordance withone or more different graphical representations on a display, andpermitting a user to modify underlying field values of the query resultset when navigating between different the representations. During anoperation, a user can run a database query. A field graph or othergraphical representation of the query results can be displayed. Therecords of the query results can be positioned about vertices, alsoreferred to as nodes, and organized according to the contents of thequery result set. For example, one or more records of the query resultset can be positioned about a particular vertex when a field value ofthe record is the same as a value corresponding to the vertex. Thedisplayed field graph can also include directed edges, or arcs,extending between the vertices to indicate possible transition paths forthe records.

A field value of one or more records can be changed by moving a recordpositioned about a first vertex to a second vertex representing adifferent field value. For example, a user can perform a drag-and-dropoperation to transition the selected record from the first vertex to thesecond vertex, or by highlighting an arc extending between the firstvertex and the second vertex. In this manner, an original field valuecan be removed from a record when the record is moved from the firstvertex to a different vertex, referred to as a second vertex.Accordingly, the record is changed to include the field valuecorresponding to the second vertex. A consistent view of the graphicalrepresentation of the query results can therefore be maintainedregardless of changes made to the records.

A user can also change between different visual representations toobtain different views of the query results. For example, a user canselect a different field type from a tab on a graphical user interface(GUI), thereby displaying a different field graph for the same queryresults. Here, the user can change one or more field values under thenewly selected field type by performing a drag-and-drop operation orhighlighting an arc in a similar manner as described above.

In another embodiment, at least one freeform vertex is provided thatdisplays a dialog box, pop-up, and the like for entering new fieldvalues, or presenting one or more other field values of the query resultset. Query result records can be modified to include the new fieldvalues by positioning the records in a region proximal to the freeformvertex, or by highlighting an arc extending between the record and thefreeform vertex, or by other approaches described herein.

Also, multiple field types can be simultaneously selected andrepresented by forming a product of field values under the field types.For example, multiple columns of a database table, each corresponding toa field type, can be selected, whereby a field graph can includevertices that each can display multiple field values, instead of asingle field value. If a record has field values that match the fieldvalues identified with the vertex, then the record is positioned in aregion proximal to that vertex. The record can be transitioned toanother vertex having multiple fields, whereby the record is updatedwith the fields of the other vertex, similar to that described hereinwith respect to other embodiments.

FIG. 1 is a block diagram of a computer system 100 in which embodimentsof the present inventive concepts can be implemented. The computersystem 100 can be a personal computer, server, smartphone, or any otherelectronic device known to those of ordinary skill in the art.

The computer system 100 includes at least one processor 102, forexample, a CPU, a memory 104, and a display 108. The memory 104 can bevolatile, for example, RAM, or non-volatile, for example, ROM, flashmemory, and the like, or a combination thereof. The memory 104 caninclude removable and/or non-removable storage media implemented inaccordance with methods and technologies known to those of ordinaryskill in the art for storing data. Stored in the memory 104 can includeprogram code, such as program code corresponding to an operating system,graphical user interface, and systems and methods in accordance with thepresent inventive concepts described herein.

The computer system 100 can include a user interface in communicationwith one or more I/O devices 106, such as a keyboard, a mouse, atrackball, and/or a touchscreen. An I/O device 106 can include aninterface for communicating with a display 108, which can present one ormore visual representations of query result data to a user in accordancewith the present inventive concepts. The computer system 100 can alsoinclude a network interface 110 that allows the computer system 100 tocommunicate with other devices via a network (not shown) such as a WAN,a LAN, the Internet, and the like, or a direct connection. The computersystem 100 can include additional hardware and/or software componentsknown to those of ordinary skill in the art, for example, one or moreconnectors such as a USB connector for coupling to other electronicdevices such as a flash memory stick.

The processor 102, memory 104, the I/O device 106, the display 108, andthe network interface 110 can communicate with each other over one ormore communications busses known to those of ordinary skill in the art,for example, a Peripheral Component Interconnect (PCI) bus.

FIG. 2 is a block diagram of a query result management system 200, inaccordance with an embodiment. The query result management system 200can execute on a computer system, for example, the computer system 100described in FIG. 1. The query result management system 200 can beconfigured to operate with a graphical user interface. Elements of thequery result management system 200 can be installed in different memorydevices of one or more computer systems. Elements of the query resultmanagement system 200 can be executed by different processors on thesame computer system or on different computer systems. Elements of thequery result management system 200 can communicate with each other viaone or more communications busses, network connectors, and/orintervening communication devices known to those of ordinary skill inthe art.

The query result management system 200 can include a database queryengine 202, a graph generator 204, a data field adjustment module 208,and a pop-up generator 214.

The database query engine 202 communicates with a database 210. Thedatabase 210 can be integrated with, and/or part of, the query resultmanagement system 200, for example, sharing the memory 104 with thequery result management system 200. Alternatively, the database 210 canbe separate from the query result management system 200, and incommunication with the query result management system 200 via a networkor other direct or indirect connection. The database 210 can include adata repository known to those of ordinary skill in the art, forexample, a relational database. The database 210 can include one or morewell-known repositories for storing user data, schemas containingmetadata, and the like.

The database query engine 202 can perform a query of the database 210 toexport data from the database 210 based on a set of user-defined searchcriteria. The database query engine 202 can communicate with a databasebrowser, editor, wizard, export tool, and the like, to perform a query,which can include specifying filter criteria, fields, and otherselection criteria related to the query, and/or view query results in adata base file, for example, a table. The database query engine 202permits a user to interact with the result set, for example, via adisplay editor.

The graph generator 204 outputs the query results to a display, forexample, a computer monitor or a touchscreen, as a graphicalrepresentation. In an embodiment, the graphical representation includesa field graph or other graph image that includes vertices and arcsextending between the vertices.

The graph generator 204 includes a vertices arrangement unit 206 thatcan display the records in the result set around a region proximal tothe vertices of the generated graph, for example, as graphical icons.The graph generator 204 can arrange the vertices in a display areaprovided by the display 108, and correct or modify the positioning ofthe individual vertices in the arrangement when vertices are added orremoved, for example, when record field values are added, removed, orchanged, whereby corresponding vertices can likewise be added, removed,or changed. When the graphical representation changes, for example, byselecting a different field type, the graph generator 204 can produce adifferent graphical representation. The graph generator 204 can alsodisplay field values that correspond to the vertices. The graphgenerator 204 can display one or more records having a common fieldvalue in a region proximal to a vertex displaying the same field value.For example, as shown in FIG. 6, a vertex entitled “Resolved,” can havea display window that includes a listing of records, e.g.,SAMPL00000003, etc. having a Resolved field value.

The graph generator 204 includes an arc arrangement unit 212 that cangenerate one or more arcs that extend between vertices. An arcrepresents a possible transition between two vertices. The positioningof the arcs can be determined from relationships between record fieldvalues of a given field types. A different graphical representation ofthe same result set can be displayed, for example, by selecting adifferent field type. Here, the arc arrangement unit 212 can change thepositioning of the arcs between vertices of the newly selected graphicalrepresentation. A record positioned at a vertex includes a field valuecorresponding to the vertex. Thus, when an arc is selected, for example,the record can be moved to a different vertex having a different fieldvalue. In an embodiment, a selected record at one end of the arc ischanged to include the field value identified at the vertex at the otherend of the arc. In another embodiment, a selected record proximal to afirst vertex at one end of the arc is dragged and dropped into a dialogbox, pop-up, and the like that is displayed at a region proximal to thesecond vertex at the other end of the arc, whereby the selected recordis changed to include the field value identified at the second vertex.

Each record includes a set of possible transition paths. A selection ofa record can therefore result in the set of possible transition pathsbeing displayed as arcs, and transition paths being formed via thedisplayed arcs to destination vertices at the other end of the displayedarcs. When a user selects a record at a vertex, arcs are drawn orhighlighted that represent the possible transition paths from the vertexto other vertices allowed on the graphical representation. For example,referring to FIG. 6, when a record identified as “SAMPL00000012” isselected, arcs can be displayed that show possible transition paths tovertices identified by “Resolved” and “Open” field values, respectively.In an embodiment, multiple records can be selected whereby anintersection of all sets for the selected records can be computed, andonly those transition paths corresponding to the selected records aredisplayed. For example, if three records are selected, and possibletransitions are displayed for only those three records. In anotherembodiment, the transition paths of all records, not just the selectedrecords, can be displayed.

The data field adjustment module 208 can change a field value of arecord to be populated with a field value identified at a vertex whenthe record is moved on a display to the vertex. The updated record canbe displayed at a field graph or other graphical representation. Forexample, if a user selects that a database table be displayed atstead ofa field graph, the updated record can be displayed at the table havingthe newly added field value.

The pop-up generator 214 produces a dialog box, pop-up window, and thelike, whereby a user can modify a result set by entering a new recordfield value. The pop-up window and the like can be located at a vertex.The new field value can be displayed at the vertex. A user cantransition a record to the vertex, for example, a window for displayingrecords having the new field value, whereby the record is updated withthe new field value. The arc arrangement unit 212 can display arcs thatshow possible transition paths from other vertices to the vertex havingthe new record field value.

FIG. 3 is a flow diagram of a method 300 for using a graphicalrepresentation of a query result set to modify query data, in accordancewith an embodiment. Some or all of the method 300 can be performed on anelectronic device comprising at least a processor and memory, such asthe computer system 100 described with reference to FIG. 1. The method300 can make use of the query result management system 200 and/or agraphical user interface, a database query application, and/or otherwell-known computer applications.

According to the illustrated embodiment, a query is performed 310 toexport or otherwise retrieve a result set from one or more storagerepositories such as the database 210 shown in FIG. 2 according touser-defined selection criteria. The result set can be organized into atable or other well-known format, and can include data, for example,meta-information about column names or other query-related information.Each row of the result set can correspond to a database record, alsoreferred to as a query result record. Each column of the result set cancorrespond to a record field type. The query result set can be displayedas a table or other well-known format on a computer display.

A field graph or other graphical representation can be generated 320from the query result data. The graphical representation can bedisplayed by selecting a record field type from a result column, a fieldpicker interface, or other user interface that displays a set of fieldsfor selection by a user. The field graph includes a plurality ofvertices. Each vertex can have at least one corresponding field value ofthe result set. The records collected from the query are visuallypresented at the vertices, according to a match between field values ofthe records and the field values corresponding to the vertices. Therecords can be arranged about the vertices of a field graph according tothe field values. The records can be listed in the display window,dialog box, pop-up window, and the like at a corresponding vertex. Therecords can be added to or removed from the display window, dialog box,pop-up window, and the like by a mouse, keyboard, or other computerinput device.

The field graph can also include a plurality of arcs that extend fromthe vertices to illustrate possible transition paths between recordspositioned in regions proximal to the vertices. The arcs can bedisplayed when the graphical representation is formed, or the arcs canbe presented upon selection of a record having a field value to bechanged.

One or more records can be selected 330 from the query result data. Asdescribed above, a field value can be displayed at a vertex of the fieldgraph indicating that each record at the vertex includes the fieldvalue. One or more query result records at the vertex can be selected,for example, using a computer input device such as a mouse or keyboard.In an embodiment, arcs are displayed showing possible paths betweenrecords in the result set, and the records are shown as icons aboutvertices. For example, when the record is selected, the relevant arcscan be highlighted to show the possible paths to other vertices wherethe selected record can be transitioned.

A field value of the selected query result record can be changed 340 toa different field value by transitioning the selected query resultrecord to a different vertex of the graphical representation. The usercan determine a transition path for the selected record by selecting anarc extending from the selected record to the destination vertex. Whenthe arc is selected, the record can be moved to a display box in aregion proximal to the destination vertex. In another embodiment, theselected record is dragged and dropped into the region proximal to thedestination vertex.

FIG. 4 is a flow diagram of a method 400 for using a graphicalrepresentation of a query result set to modify query data, in accordancewith another embodiment. Some or all of the method 400 can be performedon an electronic device comprising at least a processor and memory, suchas the computer system 100 described with reference to FIG. 1. Themethod 400 can make use of the query result management system 200,and/or a graphical user interface, a database query application, and/orother well-known computer applications.

According to the illustrated embodiment, a query result set is received410, for example, by exporting a result set in response to a query fromone or more storage repositories such as the database 210 shown in FIG.2. A query can be performed to retrieve the query result set in a mannersimilar to that described in step 310 above, and will therefore not berepeated for reasons related to brevity.

A field graph or other graphical representation of the data identifiedfrom the query result set is generated 420 and displayed on a computermonitor, touchscreen, or other display known to those of ordinary skillin the art. The field graph includes a plurality of vertices. Adifferent field value of the result set can correspond to each vertex.The field graph can be changed to a different graphical representation,for example, by selecting a different record field type at a graphicaluser interface, which can include different field values than thosedisplayed at the previous graphical representation. Accordingly, the newgraphical representation can include different vertices and/or arcs, andcan be displayed with different record field values under the differentrecord field type.

The query result records from the query result data can be arranged 430about the vertices of the field graph. Each vertex can include a displaywindow and the like that identifies a field value. A list of records canbe displayed about the vertex, each of which includes the displayedfield value.

The field graph can include at least one freeform vertex 440. A dialogbox, pop-up form, blank field, and the like can be displayed at a regionproximal to the freeform vertex for the user to enter 450 a field value.The field value can be a new field value that is added to the queryresult set. A new field value can be entered by typing it into thedialog box, or dragging the new field value from a list, table, and thelike, and dropping it into a dialog box in a region proximal to thedestination vertex. The freeform vertex 440 can be used as a catch-allor “other” category for displaying other record field values under afield type where there are too many field values to display. Transitionarcs can extend to the freeform vertex from other vertices in the fieldgraph. At least one record can be selected 460. The selected record canbe transferred to the dialog box of the freeform vertex having the newfield value by highlighting the arc between the source and destinationvertices, or by a drag-and-drop operation, i.e. using an input devicesuch as a mouse to drag the selected record from its original vertexinto the freeform vertex. Accordingly, the record can be modified 470 toinclude the new field value displayed at the destination vertex.

FIG. 5 is a screenshot of a query result set displayed at a databasefile 500, in accordance with an embodiment. The database file 500 can bedisplayed at one or more different formats by the query resultmanagement system 200 using a data visualization program such as aspreadsheet application, workflow automation application, changemanagement application, and the like, for example, IBM® Rational®ClearQuest®. One format can include a table organized into rows andcolumns. Each row can correspond to a record, for example, record 502.Each column can correspond to a record field type, for example, a fieldtype 504 entitled “State.” Each record includes a plurality of fields,which can be populated with field values. For example, record 502includes a field value 506 “Submitted” under the field type 504 entitled“State.” The field values can be available for graphing, for example,presented in a field graph shown in FIG. 6. A user can select one ormore rows and/or columns of the database file 500, and submit a requestto generate a field graph from the contents of the selected contents tothe query result management system 200, or a data visualization programin communication with the query result management system 200.

FIG. 6 shows the query results of FIG. 5 arranged in a field graph 600,in accordance with embodiment. The field graph 600 can be displayedusing a data visualization program in communication with a graphicaluser interface, for example, an IBM® Rational® ClearQuest® application.The field graph 600 can be generated according to a field type selectedby a user. For example, when the field type 504 entitled “State” isselected, the field graph 600 can display a status of a software bug(i.e., Submitted, Resolved, etc.). The state field values, i.e.,Submitted, Resolved, etc., can be determined from a result column of aquery result set. Accordingly, the field graph 600 can be displayed at asimilar manner as a state diagram. For example, transition arrows 604extend between vertices 602, 606 to indicate a possible transitionbetween states, i.e. vertices, for a record located at the vertex 602.Each vertex corresponds to a record field value. Thus, the location of arecord is determined by a match between a state field value of therecord and the state identified at the vertex.

In one example, the Submitted record field value 506 is positioned at avertex 602 of the field graph 600. In another example, the Open recordfield value 608 is positioned at a vertex 606. The record field valuescan be displayed at a window or box, for example, display window 610,proximal to the vertices. A listing of records having the field valuescan be listed in the window or box, for example, record 502.

When a record 502 entitled “SAMPL00000011” of the query results isselected, transition arrows 604 can be generated that indicate possibletransitions to vertices having state field values Open and Resolved,respectively.

A user can change the state field value of the record 502 by selecting ahighlighted arrow 604 or dragging the selected record 502 to the vertex606. Accordingly, the state field value of the record 502 can be changedfrom “Submitted” to “Open,” as shown in the field graph 700 of FIG. 7.

FIG. 8 shows the query results of FIG. 5 arranged in a field graph 800,in accordance with another embodiment. The field graph 800 can bedisplayed using a data visualization program, for example, describedherein.

Here, a different graphical representation of the query results of FIG.5 is shown than the graphical representations of FIGS. 6 and 7. Namely,a field type 804 entitled “Priority” is selected instead of the fieldtype 504 entitled “State” of the field graphs 600, 700 shown in FIGS. 6and 7, respectively. By selecting different field types in this manner,users can easily switch between different representations of the samequery results. Each graphical representation can display different fieldvalues, depending on the selected field type. For example, in FIG. 8,record 502 of the query results is shown having a record field value806, i.e., “None”, under the Priority field type.

FIG. 9 shows the query results of FIG. 5 arranged in a field graph 900,in accordance with another embodiment. The field graph 900 can bedisplayed at accordance with the method 400 described herein withreference to FIG. 4. The field graph 900 can be displayed using a datavisualization program, for example, described herein.

The field graph 900 can include a pop-up window, dialog box, blankfield, and the like for entering new field values. For example, a value904 called “Enhancements” can be added to the “Other” dialog box 902,which is used as a catch-all field for entering new field values.Alternatively, the freeform vertex 440 can be used for displaying a listof records having field values that are not assigned to a vertex, forexample, where there are too many field values under the displayed fieldtype. Transition arcs 906 can extend to the freeform vertex from othervertices. For example, an arc 906 can extend from the dialog box 908include a “None” field value. Records can be selected from the Nonedialog box 908, for example, record 910, and transferred to the dialogbox 902 by selecting the arc 906 or a drag-and-drop operation. TheEnhancements value 904 can be added under the Priority field type 804.The title of the dialog box 908 can be changed from “Other” to“Enhancements.” A new “Other” dialog box can be generated at the fieldgraph 900 to replace the dialog box 902 reconfigured for theEnhancements value, for example, by a user-selectable option in the userinterface.

FIG. 10 is an illustration of the query results of FIG. 5 arranged inanother field graph, in accordance with an embodiment. In an embodiment,multiple field types are selected, which can correspond to multiplecolumns of the database file 500. For example, the Priority field type1004 and the State field type 1006 can both be selected. A field graphcan be generated that represents the field values of each field type byforming a product of the field values. For example, vertices can begenerated that display “Resolved/Normal,” 1008 “Open/High Attention,”1010, etc. The maximum number of displayed vertices can be predefined. Auser can select combinations of certain field values to be displayedabout vertices. The field graph can be configured such that a number offield values and/or a number of vertices do not exceed a predeterminednumber. A separate vertex can also be displayed, which includes theremaining field value combinations, for example, less relevantcombinations. This vertex can be identified by a generic term such as“Others,” instead of identifying the remaining field value combinations.Any records having such combinations can be located in a region proximalto this vertex.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device. Program codeembodied on a computer readable medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, etc., or any suitable combination of theforegoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computer, other programmable data processing apparatus, orother devices to cause a series of operational steps to be performed onthe computer, other programmable apparatus or other devices to produce acomputer implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the invention has been shown and described with reference tospecific embodiments, it should be understood by those skilled in theart that various changes in form and detail may be made therein withoutdeparting from the spirit and scope of the invention.

What is claimed is:
 1. A method for changing query result datagraphically displayed on an electronic device, comprising: performing aquery of a data repository; displaying a graphical representation of aset of query results identified from the query, the set of query resultsincluding a plurality of query result records, the graphicalrepresentation including a first location corresponding to a firstrecord field value and a second location corresponding to a secondrecord field value; displaying at a first location at least one queryresult record having the first record field value; selecting a queryresult record of the at least one query result record having the firstrecord field value; changing a field value of the selected query resultrecord from the first record field value to the second record fieldvalue by transitioning the selected query result record to a secondlocation of the graphical representation; displaying a plurality offield types; selecting at least two field types of the plurality offield types; and displaying a graphical representation of the queryresults, the graphical representation including a plurality of vertices,each vertex corresponding to a product of a field value of each of theat least two field types.
 2. The method of claim 1, wherein thegraphical representation includes a field graph.
 3. The method of claim1, wherein a window is displayed at the second location, and wherein thesecond record field value is added to the selected query result recordby positioning the selected query result record in the window.
 4. Themethod of claim 1, wherein a listing of records having the first recordfield value is displayed at the first location, and a listing of recordshaving the second having the second record field value is displayed atthe second location.
 5. The method of claim 1, wherein the firstlocation includes a first node and the second location includes a secondnode, and wherein displaying the graphical representation comprisesdisplaying an arc between the first node and the second node.
 6. Themethod of claim 5, wherein changing the field value of the selectedquery result record from the first record field value to the secondrecord field value comprises selecting the arc to transition theselected query result record from the first node to the second node. 7.The method of claim 1, wherein changing the field value of the selectedquery result record from the first record field value to the secondrecord field value comprises: removing the selected query result recordfrom the first location: performing a drag-and-drop operation totransition the selected query result record to the second location. 8.The method of claim 1 further comprising: displaying a graphical userinterface; selecting a first field type of the plurality of field typesto display the graphical representation of the query results; andselecting a second field type of the plurality of field types to displaya different graphical representation of the query results.
 9. The methodof claim 8, wherein selecting the second field type of the plurality offield types comprises: selecting a query result record of the pluralityof query result records having a third record field value, the selectedquery result record displayed at a third location of the differentgraphical representation corresponding to the third record field value;and changing a field value of a selected query result record from thethird record field value to a fourth record field value by transitioningthe selected query result record to a fourth location of the differentgraphical representation corresponding to the fourth record field value.10. The method of claim 1, wherein the second location includes amodifiable field, and wherein changing the field value of the selectedquery result record comprises entering the second record field valueinto the modifiable field.
 11. The method of claim 10, furthercomprising: presenting a dialog box at the second location; entering thesecond record field value in the dialog box.
 12. The method of claim 1,wherein the at least two field types are selected from columns of adatabase file, each column corresponding to a field type.
 13. The methodof claim 1, wherein the at least two field types are selected at agraphical user interface displaying the field types.
 14. A method forchanging query result data graphically displayed on an electronicdevice, comprising: performing a query of a data repository; displayinga graphical representation of a set of query results identified from thequery, the set of query results including a plurality of query resultrecords, the graphical representation including a first nodecorresponding to a first record field value; displaying at a regionproximal to the first node at least one query result record having thefirst record field value; displaying at a region proximal to the secondnode a modifiable field; entering a second record field value into themodifiable field, the second node corresponding to the second recordfield value; selecting a query result record of the at least one queryresult record having the first record field value; changing a fieldvalue of a selected query result record from the first record fieldvalue to the second record field value by transitioning the selectedquery result record to the region proximal to the second node displayingthe modifiable field; displaying a plurality of field types; selectingat least two field types of the plurality of field types; and displayinga graphical representation of the query results, the graphicalrepresentation including a plurality of nodes, each node correspondingto a product of a field value of each of the at least two field types.15. The method of claim 14, wherein the graphical representationincludes a field graph.
 16. The method of claim 14, wherein a dialog boxis displayed at the region proximal to the second node, and wherein thesecond record field value is inserted into the selected query resultrecord by positioning the selected query result record in the dialogbox.
 17. The method of claim 14, wherein changing the field value of theselected query result record from the first record field value to thesecond record field value comprises: displaying an arc between the firstnode and the second node; and selecting the arc to transition theselected query result record from the first node to the second node. 18.The method of claim 14, wherein changing the field value of the selectedquery result record from the first record field value to the secondrecord field value comprises: removing the selected query result recordfrom the region proximal to the first node: performing a drag-and-dropoperation to move the selected query result record to the second node.19. The method of claim 14 further comprising: displaying the graphicalrepresentation of the set of query results at a graphical userinterface; selecting a first field type of the plurality of field typesto display the graphical representation of the set of query records; andselecting a second field type of the plurality of field types to displaya different graphical representation of the set of query records. 20.The method of claim 19, wherein selecting a second field type of theplurality of field types to display a different graphical representationof the set of query records comprises: selecting a query result recordof the plurality of query result records having a third record fieldvalue, the selected query result record displayed at a region proximalto a third node of the different graphical representation correspondingto the third record field value; and changing a field value of theselected query result record from the third record field value to afourth record field value by transitioning the selected query resultrecord to a region proximal a fourth node of the different graphicalrepresentation corresponding to the fourth record field value.
 21. Themethod of claim 14, wherein a dialog box is displayed at the regionproximal to the second node permitting a user to enter the second recordfield value.